Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-252915 | TOSS-04-010040 | SV-252915r824069_rule | Medium |
Description |
---|
Even though the communications channel may be encrypted, an additional layer of security is gained by extending the policy of not logging on directly as root. In addition, logging on with a user-specific account provides individual accountability of actions performed on the system. |
STIG | Date |
---|---|
Tri-Lab Operating System Stack (TOSS) 4 Security Technical Implementation Guide | 2022-08-29 |
Check Text ( C-56368r824067_chk ) |
---|
Verify remote access from outside the system using SSH prevents users from logging on directly as "root." Check that SSH prevents users from logging on directly as "root" with the following command: $ sudo grep -i PermitRootLogin /etc/ssh/sshd_config PermitRootLogin no If the "PermitRootLogin" keyword is set to "yes", is missing, or is commented out, and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding. |
Fix Text (F-56318r824068_fix) |
---|
Configure TOSS to stop users from logging on remotely from outside of the cluster as the "root" user via SSH. Edit the appropriate "/etc/ssh/sshd_config" file to uncomment or add the line for the "PermitRootLogin" keyword and set its value to "no": PermitRootLogin no The SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command: $ sudo systemctl restart sshd.service |